Skip to content

[release-4.18] OCPBUGS-58135: packages-openshift.yaml: bump OVS version to 3.5. #1828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-bot merged 1 commit into from
Jun 26, 2025
Merged

[release-4.18] OCPBUGS-58135: packages-openshift.yaml: bump OVS version to 3.5. #1828

openshift-merge-bot merged 1 commit into from
Jun 26, 2025

Conversation

@igsilya
Copy link
Contributor

@igsilya igsilya commented Jun 26, 2025

ovn-kubernetes container image moved to OVS 3.5 in: openshift/ovn-kubernetes#2593 as part of 4.19 to 4.18 sync: https://issues.redhat.com//browse/OCPBUGS-48710

We should keep OVS versions between os and ovn-k in sync in order to decrease the number of variables in the system.

CC: @sdodson @tssurya @abhat

@igsilya
packages-openshift.yaml: bump OVS version to 3.5.
4450f39 
ovn-kubernetes container image moved to this version in:
  openshift/ovn-kubernetes#2593

While not strictly necessary, we should keep OVS versions between
os and ovn-k in sync in order to decrease the number of variables
in the system.

Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 26, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 26, 2025

@igsilya: This pull request references Jira Issue OCPBUGS-58135, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-58135 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

ovn-kubernetes container image moved to OVS 3.5 in: openshift/ovn-kubernetes#2593 as part of 4.19 to 4.18 sync: https://issues.redhat.com//browse/OCPBUGS-48710

We should keep OVS versions between os and ovn-k in sync in order to decrease the number of variables in the system.

CC: @sdodson @tssurya @abhat

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from jmarrero and jschintag June 26, 2025 08:47
@igsilya
Copy link
Contributor Author

igsilya commented Jun 26, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 26, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 26, 2025

@igsilya: This pull request references Jira Issue OCPBUGS-58135, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-48709 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-48709 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jun 26, 2025
@openshift-ci openshift-ci bot requested a review from mike-nguyen June 26, 2025 08:55
@igsilya igsilya mentioned this pull request Jun 26, 2025
Merged
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 26, 2025

@igsilya: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@sdodson
Copy link
Member

sdodson commented Jun 26, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 26, 2025
@sdodson sdodson added approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Jun 26, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 26, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: igsilya, sdodson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 7056860 into openshift:release-4.18 Jun 26, 2025
5 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 26, 2025

@igsilya: Jira Issue OCPBUGS-58135: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-58135 has been moved to the MODIFIED state.

Details

In response to this:

ovn-kubernetes container image moved to OVS 3.5 in: openshift/ovn-kubernetes#2593 as part of 4.19 to 4.18 sync: https://issues.redhat.com//browse/OCPBUGS-48710

We should keep OVS versions between os and ovn-k in sync in order to decrease the number of variables in the system.

CC: @sdodson @tssurya @abhat

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@sdodson
Copy link
Member

sdodson commented Jul 3, 2025

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Jul 3, 2025

@sdodson: new pull request created: #1839

Details

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jul 3, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jmarrero jmarrero Awaiting requested review from jmarrero

@jschintag jschintag Awaiting requested review from jschintag

@mike-nguyen mike-nguyen Awaiting requested review from mike-nguyen

Assignees

@sdodson sdodson

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@igsilya @openshift-ci-robot @sdodson @openshift-cherrypick-robot